network interface bonding config
Configure the network bonding interface. There are multiple modes available.
User access
admin
Syntax
network interface bonding config -ip <IP> -netmask <IP> -devices <devices> [-gateway <IP>] [-mode <mode>] [-name bond<n>]
Argument(s) | Shortcut | Description |
---|---|---|
-devices <devices> | -d | Specifies the network devices to assign to the bonded device. Use a comma-separated list of valid devices. Valid Values: - eth0 - eth1 - eth2 (ProtectServer 3+ External only) - eth3 (ProtectServer 3+ External only) If you are using a ProtectServer 3+ External with an appliance software version older than ProtectServer 3 Network HSM Appliance Software 7.3.0, a maximum of two network devices can be bonded to a single interface. If you are using a ProtectServer 3+ External with ProtectServer 3 Network HSM Appliance Software 7.3.0 or newer, up to four devices can be bonded to up to two interfaces. |
-gateway <IP> | -g | Specifies the gateway to assign to the bonded device. |
-ip <IP> | -i | Specifies the IP address to assign to the bonded device. Configure network interface bonding with static IPv4 addresses only. If DHCP is used, the bond will be broken if one interface is assigned a different IP. |
-mode <mode> | -m | Specifies the bonding mode (default: 0). Valid Values: - 0: Balance Round Robin. Packets are transmitted alternately on each device in the bond, providing load balancing and fault tolerance. - 1: Active-Backup. One bonded device is active and the other serves as a backup. The backup only becomes active if the active device loses connectivity. - 3: Broadcast. All packets are transmitted on both bonded interfaces, providing fault tolerance. - 4: 802.3ad (Dynamic Link Aggregation). Creates aggregated groups that share the same speed and duplex settings. This mode requires a switch that supports IEEE 802.3ad dynamic links. The device used for an outgoing packet is selected by the transmit hash policy (by default, a simple XOR). This policy can be changed via the xmit_hash_policy option. Check the 802.3ad standard to ensure that your transmit policy is 802.3ad-compliant. In particular, check section 43.2.4 for packet mis-ordering requirements. Non-compliance tolerance may vary between different peer implementations. - 5: Balance TLB (Transmit Load Balancing). Outgoing traffic is distributed according to the current load and queue on each bonded device. Incoming traffic is received by the current device.- 6: Balance ALB (Adaptive Load Balancing). Both outgoing and incoming traffic is load-balanced like outgoing traffic in mode 5. Incoming load balancing is governed by ARP negotiation. The bonding driver intercepts the ARP replies sent by the appliance and overwrites the source hardware address with the unique hardware address of one of the bonded devices. Different clients will therefore use different hardware addresses for the appliance. |
-name bond<n> | -na | Specifies the name to assign to the bonded device. Valid value is bond<n>, where n is an integer from 0 to 9. This option is only available when using ProtectServer 3 Network HSM Appliance Software 7.3.0 or newer. |
-netmask <IP> | -n | Specifies the network mask, in dotted-decimal format (for example, 255.255.255.0), to assign to the bonded device. |
Example
psesh:>network interface bonding config -ip 192.20.11.10 -netmask 255.255.255.0 -mode 1 -devices eth0,eth1
NIC Bonding configured
Command Result : 0 (Success)